Personal medical information storage device and system

ABSTRACT

A subscription-based personal medical information storage device comprises a data storage unit comprising a computer readable storage medium configured to store medical and non-medical information of a user, and facilitate the retrieval of medical and non-medical information of the user from a remote medical information storage device. The data storage unit is configured to automatically run an authentication routine upon connection with the general purpose computing device to confirm that the personal medical information storage device is neither lost nor stolen before granting access thereto. A communication module is configured to facilitate a communication connection with the remote medical information storage device, and wherein the remote medical information storage device comprises an advertisement module.

BACKGROUND

Emergency responders often encounter the challenge of administering aidto unconscious patients, or patients that are not lucid. Such situationspresent challenges related to unknown allergies, existing conditions,and medications already in the patient's system, among other things.

Another challenge facing emergency responders is ensuring thatinformation provided is up-to-date and accurate. For instance, a numberof medical information storage devices exist on the market, but areoften of little use to emergency responders because the informationcontained thereon may be woefully out-of-date.

Physicians, on the other hand, are forced to deal with the challenge ofcollecting vast amounts of information from patients prior toappointments and in conjunction with treatments. For instance, prior toa first appointment with a physician, patients may be asked to spendover a quarter of an hour filling out paper work that they may havefilled out before and may be asked to fill out again.

Users often face the challenge of storing important medical (andnon-medical) documents in one central, secure location that may bereadily accessed when needed, such as at a doctor's appointment, amongother things. Additionally, such important medical and non-medicalinformation is invariably not accessible when it is needed most.

A large number of potential solutions to the above problems have beenproposed, but one of the largest challenges for companies seeking tomarket a product is covering operating costs. For example, theinfrastructure to store and transmit large amounts of medical data maybe expensive to set up and maintain.

SUMMARY

There is a need for a device and a system configured to store medicaland non-medical information in a secure, centralized location. There isalso a need to create a device and system that may permit physicians toquickly and efficiently share information, and for patients to transferinformation to different physicians. There is also a need for a systemand device configured to ensure that information stored thereon isup-to-date and current. Finally, there is a need for a device and systemthat offers financing options that may make the manufacture, marketing,sale, and operation thereof financially realizable.

A subscription-based personal medical information storage deviceincludes a data storage unit having a computer readable storage mediumconfigured to store medical and non-medical information of a user, andfacilitate the retrieval of medical and non-medical information of theuser from a remote medical information storage device. The data storageunit is configured to be read by a general purpose computing device, andthe data storage unit is configured to automatically run anauthentication routine upon connection with the general purposecomputing device to confirm that the personal medical informationstorage device is neither lost nor stolen before granting accessthereto. The data storage unit further includes a communication moduleconfigured to facilitate a communication connection with the remotemedical information storage device, and wherein the remote medicalinformation storage device comprises an advertisement module configuredto: (a) prompt a user for authorization to parse the medical informationof the user to provide personalized advertisements and recommendationsin exchange for a reduced cost subscription plan, (b) upon reception ofuser authorization, parse the medical information of the user tofacilitate the identification of relevant advertisements, (c) presentthe user with at least one relevant advertisement, and (d) offer areduced cost subscription plan or service credit to the user.

A medical information storage system includes a medical informationstorage server configured to store medical and non-medical informationfrom users of the medical information storage system, a personal medicalinformation storage device configured to exchange information with themedical information storage server and to store medical and non-medicalinformation in a computer readable storage medium. The medicalinformation storage server includes an advertisement module configuredto parse medical and non-medical information stored on the medicalinformation storage server and the personal medical information storagedevice, and to facilitate the identification of at least one relevantadvertisement or recommendation for a user based upon the medical andnon-medical information of the user. The medical information storageserver also includes communication module configured to communicate theat least one relevant advertisement or recommendation to the user.

A personal medical information storage device includes a computerreadable storage medium configured to store both medical and non-medicalinformation. An authentication module is stored on the computer readablestorage medium. The authentication module is configured to communicatewith a remote medical information storage device and verify that thepersonal medical information storage device has not been reported (a)lost, or (b) stolen, and wherein the authentication module is configuredto erase the medical and non-medical information of the computerreadable storage medium upon a determination that the medicalinformation storage device has been lost or stolen. The personal medicalinformation storage device also includes a physician note module storedon the computer readable storage medium and includes an encryptedphysician notes field, an encrypted physician files field for images andPDFs, a save functionality configured to restrict access to theencrypted physician notes field and the encrypted physician files fieldto read-only access and delete-only access, and a form module configuredto store a plurality of doctor-specific forms for downloading on ageneral purpose computing device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a representation of personal medical information storagesystem.

FIG. 2 is a block diagram representation of a remote medical informationstorage device.

FIG. 3 is a block diagram representation of a personal medicalinformation storage device.

FIGS. 4 a and 4 b are an illustration of a personal medical informationstorage device.

FIGS. 5 a and 5 b are an illustration of another personal medicalinformation storage device.

FIGS. 6 a and 6 b are an illustration of yet another personal medicalinformation storage device.

FIG. 7 illustrates a method of using a personal medical informationstorage device.

FIG. 8 illustrates a method of authenticating a personal medicalinformation storage device.

FIG. 9 illustrates a method of receiving authorization for anadvertisement-subsidized service plan of a personal medical informationstorage device.

FIG. 10 illustrates a method of receiving an opt-out request for anadvertisement-subsidized service plan of a personal medical informationstorage device.

FIG. 11 illustrates a method of prompting a user to update the personalmedical and non-medical information of a personal medical informationstorage device.

FIG. 12 illustrates a method of prompting data entry for a personalmedical information storage device.

FIG. 13 is an example of a screen shot presenting basic personal medicalinformation.

FIG. 14 is an example of a screen shot presenting documents saved to apersonal medical information storage system.

FIG. 15 is an example of a screen shot presenting physician notes assaved to a personal medical information storage system.

FIG. 16 is an example of a screen shot presenting pet or animalinformation.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof, and in which is shown byway of illustration specific embodiments in which the invention may bepracticed. These embodiments are described in sufficient detail toenable those skilled in the art to practice the invention, and it is tobe understood that other embodiments may be utilized and that variouschanges may be made without departing from the spirit and scope of thepresent invention. The following detailed description is, therefore, notto be taken in a limiting sense.

FIG. 1 illustrates a medical information storage system 100 comprising anetwork 105 connecting client devices 125 a-125 d to a network interfaceserver 115. A personal medical information storage device 110 may beconnected to a client device 125 a-125 d. Personal medical informationmay be stored on personal medical information storage device 110 orremotely in a database 120. Database 120 may be stored on networkinterface server 115, or may be stored on a separate server or servers.

Network 105 may be any form of network such as, for example, a privateIP network, a WAN, a LAN, an intranet, or the Internet, among otherthings. Of course, any other number of possible network embodiments arecontemplated by the present disclosure. Each respective connection tonetwork 105 of client devices 125 a-125 d and network interface server115 may be any form of wired or wireless connection. For instance,client device 125 a may be connected to network 105 via a wiredconnection, such as a DSL, cable broadband, or dial-up connection, or awireless connection such as a GSM, Wi-Fi, or satellite connection, amongother things. Analogously, network interface server 115 may be connectedto network 105 via a wired or wireless connection.

Network interface server 115 may be any number of appropriate servers.For instance, in one embodiment, network interface server 115 may be anhttp server. FIG. 1 illustrates a handful of client devices 125 a-125 dthat represent various possible computing devices that may be used inconnection with personal medical information storage device 110according to the present disclosure. For instance, client device 125 a(a desktop computer) represents a PC, Mac, Linux or other appropriateclient device; client device 125 b represents a laptop computer orpossibly a netbook; client device 125 c represents a tablet device suchas an iPad®; and client device 125 d represents a PDA or smartphonedevice. Client devices 125 a-125 d may comprise USB, mini-USB, cardreader, or other I/O connections that may facilitate connecting personalmedical information storage device 110 thereto.

In operation, personal medical information storage device 110 may beconnected to a client device 125 a-125 d to facilitate personal medicalinformation storage and entry. For instance, a user may connect personalmedical information storage device 110 into client device 125 a, and maythereafter input personal medical information to be saved and stored onthe personal medical information storage device 110. Thereafter,personal medical information storage device 110 may be carried on orwith the user and may be relied upon to assist in transferring sensitiveand essential personal medical information should the need arise. Forinstance, the user may have a doctor's appointment or may be injured ina car accident. In the former case, the user may allow an assistant atthe doctor's office to access the data stored on personal medicalinformation storage device 110 to facilitate the transfer of necessaryinformation that may be used to provide efficient service and care. Inthe case of a car accident, emergency responders may be able to read thedata stored on personal medical information storage device 110 to assistthe user. Clearly, these two examples are intended to facilitateunderstanding and are not to be interpreted restrictively. Indeed, anynumber of possible uses are contemplated by the present disclosure.

In one embodiment, upon connection of personal medical informationstorage device 110 with client device 125 a or 125 b (for example), anautorun routine contained on personal medical information storage device110 may run and verify a connection with network interface server 115and database 120 (or attempt to establish a connection thereto),exchange information, and verify that personal medical informationstorage device 110 is not lost or stolen, for example. In anotherembodiment, the personal medical information on personal medicalinformation storage device 110 may be compared with the personal medicalinformation in database 120 to verify that the information isup-to-date. For instance, if the information on personal medicalinformation storage device 110 is determined to be out-of-date (ascompared to the information in database 120), then the relevantinformation may be transferred to personal medical information storagedevice 110, or vice versa.

In yet another embodiment, once personal medical information storagedevice 110 is connected to a client device, such as client device 125 a,personal medical information storage device 110 or network interfaceserver 115 may determine that the client device 125 a is that of aparticipating service provider, and may apply a predetermined providerlayer in order to facilitate and standardize the presentation of theuser's medical information. For instance, a participating serviceprovider may have a corresponding user interface layer thatautomatically formats the user's medical information into the provider'spreferred intake form, among other things. The provider layer may alsofacilitate data display and entry to enable the provider and his or herstaff to update a personal medical information storage device 110 withany number of relevant data and information such as, for example,X-rays, diagnoses, medication histories, allergies, appointments, andphysician notes, among other things.

In another embodiment, personal medical information storage device 110may be a card with a URL and a member number that, rather than requiringa provider to insert personal medical information storage device 110directly into a client device 125 a, may permit the service provider torapidly and easily access a remote website with the user's personalmedical information stored thereon. For instance, in one example, if auser is injured and unconscious or not otherwise lucid, emergencyresponders may be able to enter a URL into their client device (such asclient devices 125 a-125 d) and enter the user's ID number to retrieve alist of allergies and vital personal medical information to facilitatetheir tasks. Alternatively, personal medical information storage device110 may comprise a bar code or QR Code to be scanned and quickly takeemergency responders to a page displaying the user's basic personalmedical information.

FIG. 2 is a block diagram representation of a remote medical informationstorage device 200. Remote medical information storage device 200comprises a user database 205, an encryption module 210, an I/O module215, an advertisement module 220, an authentication module 225, amedical data module 230, a physician note module 235, a file storagemodule 240, a provider database 245, a mobile app module 250, asubscription module 255, and a processor 260. Each module 205-255 ofremote medical information storage device 200 is connected to processor260 in order to facilitate access to and use thereof.

Remote medical information storage device 200 may be a server or anynumber of servers that store medical information remotely. User database205 may be a single database or any number of databases configured tostore user data including, but not limited to, user names, ID numbers,passwords, and medical and non-medical information, among other things.User database 205 may reside on a single remote medical informationstorage device 200, across multiple remote medical information storagedevices 200, or even multiple remote computers (e.g., for instance, thepassword database may reside on a company server and the remainingmodules on a health provider's server). User database 205 may beconnected to a processor 260 for data processing.

Encryption module 210 represents any module related to data encryption.For instance, it may be beneficial to encrypt data as it is transferredbetween network interface server 115 and client devices 125 a-125 d.Encryption may also be beneficial for data stored on personal medicalinformation storage device 110 or in database 120. For example,unencrypted data may be accessed and stolen or read, while encryptingdata may serve as an additional layer of protection to avoid data theft.Encryption module 210 may be connected to processor 260. Data may betransferred between modules, such as between user database 205 andencryption module 210, via processor 260.

I/O module 215 represents any module configured to control the I/Ointerface of remote medical information storage device 200. I/O module215 is connected to processor 260 to enable the communication ofmodules, among other things. For instance, I/O module 215 may enablecommunication of data with user database 205 and a client device 125 a,via processor 260. Generally speaking, I/O module 215 operatesconsistent with a general understanding of the term.

Advertisement module 220 represents a module configured to enableproduct advertisements and recommendations. Advertisement module 220 isconnected to processor 260 and is therefore in communication with theother modules of remote medical information storage device 200. Forinstance, advertisement module 220 may exchange data with user database205 in order to assess a given user's relevant medical needs and topropose relevant advertisements and recommendations. In one example, adiabetic may receive an advertisement related to a new insulin test. Inanother example, a user with high blood pressure may be informed of anew blood pressure medication. In yet another embodiment, users mayreceive advertisements or recommendations directly from their healthcare providers. For instance, a physician may desire to remind a patientto seek a refill after a predetermined period of time has elapsed, andtherefore, advertisement module 220 may be configured to facilitate suchreminders. Of course, as may be readily from the present disclosure, anynumber of possible uses of advertisement module 220 are contemplated bythe present disclosure. The preceding examples are provided as a few ofthe possibilities intended.

Authentication module 225 represents a module configured to authenticatea personal medical information storage device 110. For instance, when apersonal medical information storage device 110 is read by a clientdevice 125 a, prior to allowing access to the personal medicalinformation storage device 110 remote medical information storage device200 may verify that the personal medical information storage device 110has not been reported lost or stolen. The authentication module 225 mayauthenticate using any suitable authentications means. For instance, anauthentication script or routine in any possible form may be employedand is contemplated by the present disclosure. As used herein,authentication routine refers to any possible form of authenticationused to verify the status of a personal medical information storagedevice 110. In one embodiment, if it is determined that the personalmedical information storage device 200 has been reported lost or stolen,authentication module 225 may transmit a command to wipe or erase thedata stored on the personal medical information storage device 200.Otherwise, authentication module 225 may grant access to the informationcontained on personal medical information storage device 110.

Medical data module 230 represents a module configured to store medicaldata. In some cases, a user's medical data may be stored in userdatabase 205; however, in other cases it may be desirable to storemedical data in a dedicated medical data module 230. Medical data module230 may also be used to store provider information such asprovider-specific medical forms. Medical data module 230 is connected toprocessor 260 in order to enable communication between modules. In oneembodiment, medical information may be transferred from I/O module 215to medical data module 230 via processor 260.

Physician note module 235 represents a module configured to storephysician notes. For example, a physician may draft and store a noteregarding, for instance, a diagnosis to facilitate the exchange ofinformation with other physicians. In one embodiment, physician notemodule 235 may be configured such that once a physician saves a note, itmay not be edited. Physician note module 235 may be configured toencrypt and otherwise store physician notes with protection. Physiciannote module 235 may protect sensitive information by any suitable means.For instance, in one example, physician note module 235 may compriseUNIX-like permissions and may only grant read permissions.Alternatively, physician note module 235 may also permit the deletion,but deletion only, of physician notes. In another example, physiciannote module 235 may comprise Microsoft or IBM DOS variant attributes torestrict access to read-only or delete-only access. Of course, thepreceding are merely illustrative examples not intended to be taken in alimiting sense.

File storage module 240 represents a module configured to store userfiles such as, for example, images, and PDFs, among other things. Forinstance, a user may desire to store a birth certificate, copies ofvaccination records, or non-medical information such as copies ofinsurance policies, lists of valuables, and living wills, among otherthings.

Provider database module 245 represents a module related toprovider-specific information. In one embodiment, a provider maypre-load predetermined information and files such as, for example,specific forms and pamphlets. Provider database module 245 may alsocomprise provider layers configured to apply a standardized layerspecific to a given provider. Provider database module 245 maycommunicate with other modules of remote medical information storagedevice 200.

Mobile app module 250 represents a module configured to present thedifferent modules and information stored in remote medical informationstorage device 200 in a format for small screens such as forsmartphones. For instance, remote medical information storage device 200may determine that client device 125 d has made a request forinformation, may determine that client device 125 d is a smartphone, andmay direct all communications through mobile app module 250 to ensurethat the data appears as desired.

Subscription module 255 represents a module configured to track andmonitor a user's subscription information. For instance, in oneembodiment, when a user connects personal medical information storagedevice 110 to client device 125 a, remote medical information storagedevice 200 may send a request to subscription module 255 to confirm thatthe user has an account in good standing. In this embodiment, a userwith outstanding account issues may be prompted to take action and maybe given limited access (or no access at all) to services related to hisor her account. Otherwise, the user may be given access to his or herdata as displayed by default. In one embodiment, a subscription may berequired to access some or all of the functionality of the personalmedical information storage device 110.

FIG. 3 shows a block diagram representation of a personal medicalinformation storage device 300. Personal medical information storagedevice 300 may comprise a plurality of modules including, an I/O module305, a communications module 310, an encryption module 315, anauthentication module 320, a physician notes module 325, a protectedfiles module 330, a basic files module 335, a subscription module 340, aprovider module 345, a sport module 350, and a pet/animal module 355,among other things. Many of the modules have been discussed above inrelation to remote medical information storage device 200. The modulesmay be stored on a data storage unit, or memory unit, of personalmedical information storage device 300. For instance, in one embodiment,personal medical information storage device 300 comprises an electronic,magnetic, or resistive memory device.

Communications module 310 represents a module configured to enable thecommunication of data from personal medical information storage device300 and remote medical information storage device 200. In oneembodiment, communications module 310 may facilitate the communicationbetween a client device 125 a and a remote interface server 115. As usedherein, a communication connection is any connection configured toenable the transmission and reception of data between a personal medicalinformation storage device 300, via a client device 125 a, and a remotemedical information storage device 200, and may be established bycommunications module 310. Protected files module 330 represents amodule configured to store and facilitate access to files that have beenidentified as “protected” by the user. For instance, in one embodimentsensitive personal information, such as social security numbers, medicaland medication histories, birth certificates, among other things, may bespecially identified as “protected” and may only be accessed bypassword. On the other hand, in this embodiment, non-protected filessuch as vaccination records or any other files that the user wishes tobe accessed without having to enter a password may be stored in a basicfiles module 335.

Sport module 350 represents a module configured to store sport-specificinformation. For example, in one embodiment sport module 350 isconfigured to store data related to a user's exercise routine includinghistories, performance, and goals, among other things. Pet/animal module355 may be configured to store pet/animal-specific information such as,for example, medical history. In one embodiment, pet or animalinformation may be stored on the pet owner's device. Alternatively, petor animal information may be stored on a personal medical informationstorage device 300 stored on, for instance, a collar.

In operation, the different modules of personal medical informationstorage device 300 may work in concert with remote medical informationstorage device 200, and with corresponding modules thereof, in order tofacilitate the exchange of medical information, to ensure that a user'sinformation is up-to-date, and to protect user information against theftand loss. In one example, personal medical information storage device300 may be connected to a client device 125 a, following which, theauthentication module 320 operates to communicate with the user database205 and processor 260 of a remote medical information storage device200. Once personal medical information storage device 300 receives aconfirmation of authentication, then client device 125 a may displayinformation from basic files 335, from the physician notes 325, andprotected files 330, among other things.

Personal medical information storage device 300 may include othermodules. For instance, it may also include an update module configuredto store, organize, and detect triggering events for prompting a user toupdate his or her medical or non-medical information stored on personalmedical information storage device 300 or remote medical informationstorage device 200. In one embodiment, the update module may store aplurality of triggering events including but not limited to (a) timeelapsed since previous data entry, (b) life events, such as a birth ormarriage, (c) an upcoming appointment with a provider, or (d) a requestfrom a service provider, among other things. For instance, the updatemodule may be configured to alert a user to update personal informationif, for example, a predetermined amount of time elapses since theprevious data entry. In one embodiment, the predetermined amount of timemay be three months; or it may be one year. In another embodiment, theupdate module may be configured to prompt a user to update medical ornon-medical information at periods of the year where there may typicallybe changes, such as in September or October, after the beginning of anew school year.

In one embodiment, the update module may prompt a user to update medicaland non-medical information prior to an upcoming appointment with aprovider or at the request of a provider. For example, the update modulemay receive a communication from a remote medical information storagedevice 200 indicating an upcoming appointment with a provider, and inresponse, the update module may prompt the user to enter updated medicaland non-medical information via, inter alia, a client device 125 a.Alternatively, a provider may transmit a request, via remote medicalinformation storage device 200, to the update module to prompt a user toupdate medical or non-medical information.

The update module may also be configured to detect the arrival orpending arrival of one of the triggering events. Once, a triggeringevent is detected, the update module may prompt the user, via a pop-upon a client device 125 a, a phone call, or any other suitable means, toupdate the medical or non-medical information stored on personal medicalinformation storage device 300 and/or remote medical information storagedevice 200.

Personal medical information storage device 300 may also comprise aforms module configured to store, track, and update provider forms. Inone embodiment, personal medical information storage device 300 may comepre-loaded with at least one provider-specific form. For instance,personal medical information storage device 300 may be offered by aprovider and may already include that provider's relevant forms. In oneembodiment, the form module may include an intake form, a follow-upform, and HIPAA-related forms, among other things. The forms module mayalso be configured to establish a communications link with a remoteserver and update any forms stored in the forms module. In oneembodiment, the forms module may be configured to automatically fillportions of the forms loaded therein based on a user's medical andnon-medical information. Of course, the preceding examples are merelyprovided for illustration and are not to be taken in a limiting sense.

FIGS. 4 a and 4 b illustrate a personal medical information storagedevice 400. In one embodiment, personal medical information storagedevice 400 comprises an interface connection 405 and a wearable band410. As used herein, wearable refers to anything that may renderpersonal medical information storage device 400 suitable to be worn, orsecure to a user, such as a band, a clasp, a clip, a bracelet, or achain, among other things. Interface connection 405 may provide accessto a computer readable storage medium on which a plurality of modulesmay be stored. In one embodiment, interface connection 405 may be a USBor mini-USB plug. Alternatively, interface connection 405 may be anyform of interface configured to give client device 125 a access to thecomputer readable storage medium of the personal information storagedevice 400. For instance, in one embodiment, interface connection 405may be a SD card, a USB thumb drive, or a mini-USB thumb drive.

Interface connection 405 may be completely removable from wearable band410, or may be integrated therein and may be accessible by moving aportion of wearable band 410. For instance, in one embodiment, wearableband 410 may be a hard rubber band configured to snap out of place andreveal a USB plug (interface connection 405), and then snap back intoplace after use.

FIGS. 5 a and 5 b show a personal medical information storage device 500comprising an interface connection that may be hidden (505 b) or exposed(505 a) by removing interface connection 505 b from wearable band 510.In one embodiment, a clasp 515 may hold a computer readable storagemedium comprising an interface connection (505 a or 505 b), and theclasp may be slidably removable from wearable band 510. For instance,personal medical information may be stored on a computer readablestorage medium, such as an SD card, and held in place within a wearableband 510 by a clasp 515. For example, a first responder arriving at thescene of an accident may identify the personal medical informationstorage device 500 on an accident victim, may remove interfaceconnection 505 b to access the accident victim's vital information andfacilitate the care of the patient.

FIGS. 6 a and 6 b show a card embodiment of a personal medicalinformation storage device 600. In this card embodiment, personalmedical information storage device 600 comprises an interface connection605 a, which may be a credit card-like IC chip (such as the EMV chipsused in charge cards) and display a user name 610. Optionally, personalmedical information storage device 600 may also include a mini-USBconnection 605 b, a user photo 615, a logo 620, and/or a QR code 625.

In operation, mini-USB connection 605 b may enable connection withclient devices 125 c and 125 d, which commonly do not have full-sizedUSB plugs. Additionally, a QR code 625 may enable a person, such as anemergency responder, to scan the card and have immediate access to theuser's basic information, without having to try and create a connectionwith personal medical information storage device 600. In one embodiment,the inclusion of user photo 615 facilitates a visual confirmation thatthe personal medical information storage device 600 belongs to the user.

It is understood that personal medical information storage device 600(in any embodiment) may comprise other modules and/or functionalityincluding, but not limited to, GPS, RFID, and NFC. For instance, in oneembodiment, a GPS chip (not shown) may facilitate geospatialidentification for authorization purposes. In another embodiment, theGPS chip may be configured to provide relevant information to facilitatethe identification of relevant advertisements. Of course, a GPS chip maybe configured to provide any number of relevant functionalities and usesto a personal medical information storage device 600. In otherembodiments, radio-based close proximity transmission features andfunctionality may also be included. For instance, personal medicalinformation storage device 600 may include RFID or NFC functionality inorder to facilitate data transmission. Of course the preceding examplesare intended to illustrate the breadth of functionality envisioned bythe current disclosure, and are not to be taken in a limiting sense.

FIG. 7 illustrates one method 700 of using a personal medicalinformation device (for the purpose of the method figures, personalmedical information device 400 and client device 125 a will be referredto in a non-limiting sense). In a first method step 705, a personalmedical information device 400 is read. For instance, personal medicalinformation device 400 may be inserted into a client device 125 a. Inanother embodiment, personal medical device 400 may be read using a QRcode 625. Generally speaking, reading a device refers to any method orstep comprising accessing data or a file stored on a computer readablestorage medium.

In a next method step 710, personal medical information device 400 isauthenticated to confirm that it has been reported neither lost norstolen. For instance, in one embodiment, after personal medicalinformation device 400 is connected into a client device 125 a, aroutine may automatically run to determine whether the personal medicalinformation device 400 has been reported stolen. In other embodiments,GPS or biometrics may be relied upon to determine identity based on acombination of location and biological identification characteristics(such as fingerprints).

To the extent that personal medical information device 400 does notproperly authenticate, a wipe (or data erasure) step 715 may be run toprotect the data stored thereon. In one embodiment, if theauthentication routine receives a response indicating that the personalmedical information device 400 has been reported lost or stolen, theroutine may then automatically launch a data shredding or reformattingroutine to completely and securely erase or wipe all of the informationstored on the personal medical information storage device 400.

However, to the extent that the personal medical information storagedevice 400 authenticates properly, a next method step 720 comprisespresenting basic information to the user. For example, once the personalmedical information storage device 400 properly authenticates, thescreen of client device 125 a may display basic vital informationincluding, but not limited to, a medication log, allergies, vitalstatistics (date of birth, gender, blood type, weight and height, etc.),address, and emergency contacts, among other things. In anotherembodiment, detailed information may be password-protected.

Therefore, in a subsequent optional method step 725, the user isprompted with a password request in order to access detailed medicalinformation. In one embodiment, certain tabs and portions of the UI maycomprise lock icons suggesting the need to enter a password to accessthose particular areas of the personal medical information storagedevice 400. Once those tabs or icons are selected, the user may beprompted to enter a password. If the password does not match, then theuser may be taken back to the default page. Of course, a lock icon isnot required and may be provided for the user's benefit.

However, in one embodiment, if the password matches, a next method step730 is launched by which private or protected information is presentedto the user via client device 125 a. For instance, if the user seeks toaccess a portion of personal medical information device 400 wheresensitive financial documents are stored, and the user correctly entersthe password, then the user may next be taken to a screen where thesensitive information is presented. Otherwise, the user may be takenback to the default screen.

FIG. 8 illustrates a method 800 of authenticating a device. In a firstmethod step 805, an autorun routine may launch automatically once apersonal medical information storage device 400 is connected to a clientdevice 125 a. In a next method step 810, the routine may attempt todetermine whether or not client device 125 a has a connection to anetwork interface server 115 that may be used for the authenticationprocess. In one embodiment, the connection may comprise a connection tothe Internet. However, the connection may be any connection, be it localor remote, that allows the routine to access a database (e.g., 120)containing authorization information. If the routine determines thatthere is no remote connection, then the routine may only authorizeaccess to basic medical information (see method step 815).

If the routine determines that there is a connection to a networkinterface server 115, then a next method step 820 may comprise queryingthe network interface server 115 to determine whether the personalmedical information device 400 has been reported lost or stolen. In oneembodiment, this step may comprise transmitting a unique device-specificidentification number and cross-referencing that number with a report ofdevices that have been reported either lost or stolen. However, theauthentication step may also be accomplished based on a user name, amongother things, associated with a personal medical information device 400.

If it is determined that the personal medical information device 400 hasnot been reported lost or stolen, then the routine may send anauthorization command to the client device 125 a to authorize access tothe data contained thereon (see step 830). However, to the extent thatthe personal medical information device 400 has been reported eitherlost or stolen, the authorization routine may launch a wipe or erasureinstruction to completely erase the data stored thereon. For instance,the personal medical information storage device may automaticallyperform a reformatting operation to completely and securely erase allsensitive information.

FIG. 9 illustrates a method 900 of providing targeted advertising to auser in the form of, for instance, an advertisement-subsidized serviceplan. In a first method step 905, an advertisement authorization routine(such as a script) is run. In a next method step 910, the authorizationroutine determines whether a given user has authorized targetedadvertising. In one embodiment, when a user signs up with a personalmedical information storage system 100, the user may accept an agreementto receive a device without a monthly subscription (or with a reducedsubscription) in exchange for receiving targeted advertising based onthe user's particular medical information. If the user does authorizetargeted advertising, an advertisement authorization flag may be setindicating this authorization. Of course, any other suitable process maybe used to detect authorization.

To the extent that authorization for targeted advertisement has not beenset, then a related routine may be run to detect whether the user willauthorize the advertising module to use personal information. Forinstance, in method step 915 the system ascertains whether a request fortargeted advertisements has been made. In one embodiment, method step915 may comprise first determining whether the particular user hasalready been asked to authorize targeted advertising (via, for example,a flag or variable). If the user already has been asked and has notauthorized advertising, then the advertising routine may terminate 920.

However, to the extent that advertising authorization has not beenrequested, then the request may be made in a subsequent method step 925.For instance, the user may be prompted, via client device 125 a toapprove targeted advertising (or to opt out). If the user does notauthorize targeted advertising, then the routine may end 935. But if theuser does authorize targeted advertising, then the user may beautomatically enrolled in a reduced cost or subscription free serviceplan 940.

Once it is determined that the user has authorized a reducedsubscription service plan, then a next method step 945 may compriseparsing the user's information to identify potentially relevantadvertising. For instance, in one embodiment, the advertisement module220 may scan the different entries in the personal medical informationstorage device 400 and categorize entries by type, such as medications,allergies, chronic conditions, locality, etc. The advertisement module220 may then compare that information with a list of relevantadvertisements that may also be categorized. In another embodiment,advertisement module 220 may refer to a finite number of potentialadvertisements, categorized by type, and compare the advertisements withuser data to identify potentially relevant advertisements.

Finally, once relevant advertisements have been identified, a finalmethod step 955 comprises presenting the relevant advertisements to theuser. For instance, if the user is diabetic and advertisement module 220identifies that the user is diabetic, then the advertisement module maysend an advertisement, such as a video, to client device 125 a to enablethe user to find out about a potentially relevant product. In anotherembodiment, once a relevant match is identified, an advertisement may besent to the user via other means, such as a telephone call, mail, or anyother means.

FIG. 10 illustrates a method of prompting a user to enroll in a reducedsubscription targeted advertisement plan 1000. In a first method step, anetwork interface server 115 receives a request to purchase a personalmedical information storage device 400. This may be, for example, via awebsite, over the phone, or any other suitable means of purchasing andreceiving a request to purchase a device. In a next method step 1010,network interface server 115 prompts the entry of purchase details. Forexample, the user may be presented with a web page displaying addressand payment information, among other things.

Network interface server 115 may request that the user opt out oftargeted advertising based on the user's personal medical information(see step 1015). In one embodiment, the opt out may occur on thepurchase page via a check box. Alternatively, the opt out may berequested in a preceding or subsequent page. If the user elects to optout of the targeted advertising subscription plan, then a next step 1025may comprise prompting the entry of subscription details. For example,if the user checks the box opting out of the reduced cost subscriptionplan, then the user may be presented with a new payment page requestingthe entry of payment information for a regular subscription andauthorization to charge the user on a regular basis therefor. As usedherein, a reduced cost subscription plan may be any service plancomprising a reduction in overall cost of the plan, and may include afree service at one extreme, and slight reduction at the other extreme.In one embodiment, a reduced cost subscription plan may comprise a fullcost subscription plan in conjunction with a service credit. Forinstance, a user may receive an incremental reduction in subscriptioncost based upon, inter alia, the frequency of advertisements receivedand/or viewed.

However, if, on the other hand, the user does not opt out of the reducedsubscription plan, then the purchase of the personal medical informationstorage device 400 may be purchased after confirming the purchaseinformation and/or checking out (see step 1020).

FIG. 11 illustrates a method of prompting a user to update his or hermedical and non-medical information in a personal medical informationstorage system 100. In a first method step 1105, a user connects apersonal medical information storage device 400 into a client device 125a to initiate an update script. In a next method step 1110, the updateroutine queries whether a triggering event has occurred that would leadto a request to update information. For example, triggering events maybe the simple passage of time since the last information update, arequest by a service provider, or a schedule an appointment, among otherthings. If the routine determines that a triggering event has occurred,then the user is prompted to update his or her personal information (seestep 1120). If not, however, then the client device 125 a displays thedefault page (see step 1115).

If an update is requested, the request may come in the form of a pop-upwindow, email reminders, a telephone call, or any other suitablereminder. In one embodiment, the user may be prompted to updateinformation via a pop-up window containing a link to an “edit fields”window configured to facilitate data entry. Once edits are entered, thenthey may be saved both locally on a personal medical information storagedevice 400 and remotely in a database 120.

FIG. 12 illustrates a method of efficiently collecting information froma user. In computer parlance, such information requests and userinteractions are often accomplished by a wizard, or targeted data entryas guided by the client device 125 a, personal medical informationstorage device 400, and/or remote medical information storage device200.

The data entry wizard may be encountered at at least one of twosituations: first, when a new personal medical information storagedevice 400 is inserted into a client device 125 a for the first time;second, when a new account is created on-line (usually in conjunctionwith the purchase of a personal medical information storage device 400).Thus, method 1200 may commence with either method step 1205 a or 1205 b.Preferably, when a user purchases a new personal medical informationstorage device 400 on-line, and then enters personal information inconjunction with the purchase and account creation, that personalinformation may be automatically stored upon the personal medicalinformation storage device 400 upon delivery (or alternatively,automatically once the device is plugged into a client device for thefirst time).

In a first method step 1210, a wizard module is launched to guide theuser through the data entry process. For example, the wizard may bethrough a series of pop-up windows and questions on client device 125 a.In another embodiment, the “wizard” may consist of a guided telephonecall (either with a recorded operator, or with a live operator). In asubsequent method step 1215, the user is presented with an initialquestionnaire in order to target the questions asked by the wizard andtarget relevant information (and therefore eliminate wasted responsetime). Thus, for example, a next step 1220 may comprise requesting thatthe user identify whether or not he or she has a first condition (e.g.,diabetes). If the user answers in the affirmative, then the wizard maynext prompt more detailed questions (see step 1225) in order to fullypopulate the fields corresponding to the first condition. Otherwise, theuser may be prompted to answer a question regarding a second condition(see step 1230). Yet again, if the user answers affirmatively regardingthe second condition, then the wizard may prompt more detailedinformation regarding that condition (see step 1235). Otherwise, thewizard may prompt responses related to other conditions. Any number ofpossible conditions are contemplated by the present disclosure, but forthe purposes of brevity and avoiding unnecessary repetition, the nextstep in the method 1200 comprises prompting the user to answer aquestion as to an n condition (see step 1240). Again, if the useranswers in the affirmative as to the nth condition, then the wizard willprompt questions to fill out information related to the nth condition(see step 1245). Otherwise, the wizard may continue on to the nextmethod step. Of course, the above illustration is merely one example ofthe wizard concept and should not be taken in a limiting sense.

Once the wizard has completed its initial battery of questions, the usermay then be prompted to enter information as desired (see step 1250).For example, the user may desire to enter health insurance informationthat may not be required by the wizard, but that the user may deem to beuseful. Personal medical information storage device 400 may beconfigured to store any amount of possible medical and non-medicalinformation thereon. For instance, in an additional method step 1255,the user may elect to store documents to personal medical informationstorage device 400. In one embodiment, the documents may include birthcertificates, marriage certificates, living wills, and X-rays amongother things.

Finally, the wizard may prompt the user to save all of the informationentered in a last method step 1260.

FIG. 13 illustrates one embodiment of a default first page 1300 of apersonal medical information storage device 400 as displayed on a clientdevice 125 a. For instance, the default first page 1300 may comprise alogo 1355, any number of potential information such as, a medication log1305, an allergies log 1310, a supplement log 1315, emergency respondertargeted notes, such as a “do not resuscitate” note 1320, a vitals log1325, an emergency contact log 1330, and a special needs notes 1335. Thedefault first page 1300 may also comprise a print button 1345. In oneembodiment, the default first page comprises a list of tabs 1340, thatmay be used to organize information much like medical folders. Defaultfirst page 1300 may also include a photo identification 1350 in order tofacilitate identification. In practice, any other information that maybe important for, for example, first responders, may be included on thedefault first page 1300.

FIG. 14 illustrates one embodiment of a documents screen 1400 of thepresent disclosure. The documents screen 1400 may comprise a logo 1455that may be customized for a service provider, or may indicate themanufacturer of the personal medical information storage device 400. Thedocuments screen 1400 may be organized by the document type. Forexample, documents screen 1400 may comprise categories for personaldocuments 1405, business documents 1410, extras 1415, and otherdocuments 1420. Additionally, any other number of relevant documentcategories and classifications may be used as relevant. The documentsmay be protected by a password, and an icon 1435 may indicate that agiven document may only be accessed by entering a password. Documentsscreen 1400 may also comprise an add button 1430 to facilitate theaddition of new documents.

FIG. 15 illustrates a physician notes screen 1500 according to oneembodiment. The physician notes screen 1500 may comprise categorizedphysician notes grouped by tabs 1505. Alternatively, any suitable formof categorization may be employed. In one embodiment, once physiciannotes are created and saved, they may not be edited. In this embodiment,the notes may only viewed by clicking on a view button 1510 or deletedby clicking on a delete button 1515. Additionally, physician notesscreen 1500 may comprise a form field 1525 containing relevant formsthat the patient may fill out in advance of an appointment. In oneembodiment, the forms may be automatically populated based oninformation in the personal medical information storage system 100. Forexample, prior to an appointment, a user may be prompted to download,fill out, and bring a given form to the appointment. The form may bepre-loaded on a personal medical information storage device 400, andwhen the user opens the form, certain fields may be automatically filledrequiring the user to only fill in a limited number of fields prior tohis or her appointment.

In a pet/animal information screen 1600, information pertaining to a petor animal may be stored on a personal medical information storage device400. In one embodiment, the pet/animal information may be stored on apet owner's personal medical information storage device 400. In anotherembodiment, pet/animal information may be stored in a personal medicalinformation storage system 400 stored, for instance, in an animalcollar, among other things. The pet/animal information screen 1600 maycomprise a pet/animal data section configured to store informationrelated to the pet or animal in question. Relevant information mayinclude the species, breed, gender, weight, and vaccination records,among other things.

Although this invention has been described in terms of certain preferredembodiments, other embodiments that are apparent to those of ordinaryskill in the art, including embodiments that do not provide all of thefeatures and advantages set forth herein, are also within the scope ofthis invention. Accordingly, the scope of the present invention isdefined only by reference to the appended claims and equivalentsthereof.

What is claimed is:
 1. A subscription-based personal medical informationstorage device comprising: a data storage unit comprising a computerreadable storage medium configured to: store medical and non-medicalinformation of a user; and facilitate the retrieval of medical andnon-medical information of the user from a remote medical informationstorage device; wherein the data storage unit is configured to be readby a general purpose computing device, and further wherein the datastorage unit is configured to automatically run an authenticationroutine upon connection with the general purpose computing device toconfirm that the personal medical information storage device is neitherlost nor stolen before granting access thereto; the data storage unitfurther comprising: a communication module configured to facilitate acommunication connection with the remote medical information storagedevice, and wherein the remote medical information storage devicecomprises an advertisement module configured to: (a) prompt a user forauthorization to parse the medical information of the user to providepersonalized advertisements and recommendations in exchange for areduced cost subscription plan, (b) upon reception of userauthorization, parse the medical information of the user to facilitatethe identification of relevant advertisements, (c) present the user withat least one relevant advertisement, and (d) offer a reduced costsubscription plan or service credit to the user.
 2. Thesubscription-based personal medical information storage device of claim1 wherein the authentication routine comprises: transmitting a uniquedevice-specific identification corresponding to the subscription-basedpersonal medical information storage device to the remote medicalinformation storage device; receiving data from the remote medicalinformation storage device indicating whether the subscription-basedpersonal medical information storage device associated with thetransmitted unique device-specific identification has been reported lostor stolen.
 3. The subscription-based personal medical informationstorage device of claim 1 further configured to erase all medical andnon-medical information from the data storage unit if the authenticationroutine signals that the subscription-based personal medical informationstorage device has been reported lost or stolen.
 4. Thesubscription-based personal medical information storage device of claim1 wherein the data storage unit further comprises an update moduleconfigured to (a) detect a triggering event, (b) in response to thetriggering event, transmit an update prompt configured to request theuser to input updated information, (c) save updated information to thedata storage unit, and (d) transmit the updated information to theremote medical information storage device for remote storage.
 5. Thesubscription-based personal medical information storage device of claim4 wherein the triggering event comprises at least one of: apredetermined passage of time since a previous date of data entry; arequest from a service provider; and a scheduled appointment with aservice provider.
 6. The subscription-based personal medical informationstorage device of claim 1 configured to receive medical information froma wizard configured to (a) present a user with an initial questionnaireregarding a predetermined number of conditions, (b) receive responsesfrom the user identifying whether the user has any of the predeterminednumber of conditions, and (c) prompt user with additional questions forany of the predetermined number of conditions for which the useranswered in the affirmative.
 7. The subscription-based personal medicalinformation storage device of claim 1 further comprising a physiciannotes module configured to (a) store physician notes and files, (b)encrypt physician notes and files, and (c) grant access to physiciannotes and files only upon successfully entering a password.
 8. Thesubscription-based personal medical information storage device of claim7 further wherein the physician notes module is configured to restrictaccess to physician notes and files to read-only access and delete-onlyaccess.
 9. The subscription-based personal medical information storagedevice of claim 1 further comprising a pet/animal module configured tostore pet information including pet species and pet vaccination records.10. The subscription-based personal medical information storage deviceof claim 1 further comprising a forms module configured to storeprovider forms, and further wherein the provider forms are pre-loaded onthe subscription-based personal medical information storage device. 11.The subscription-based personal medical information storage device ofclaim 1 comprising a wearable band configured to secure thesubscription-based personal medical information storage device to auser.
 12. A medical information storage system comprising: a medicalinformation storage server configured to store medical and non-medicalinformation from users of the medical information storage system; apersonal medical information storage device configured to exchangeinformation with the medical information storage server and to storemedical and non-medical information in a computer readable storagemedium; an advertisement module configured to parse medical andnon-medical information stored on the medical information storage serverand the personal medical information storage device, and to facilitatethe identification of at least one relevant advertisement orrecommendation for a user based upon the medical and non-medicalinformation of the user; and a communication module configured tocommunicate the at least one relevant advertisement or recommendation tothe user.
 13. The medical information storage system of claim 12 furtherwherein the communication module is configured to prompt the user forauthorization to parse medical and non-medical information of the user,and wherein if the user does not provide authorization therefor, theuser is prompted to sign up for a subscription service.
 14. The medicalinformation storage system of claim 12 wherein the advertisement moduleis configured to detect whether the user has a condition including atleast one of (a) diabetes, (b) high blood pressure, or (c) depression,and present the user with a relevant product, treatment, orrecommendation.
 15. The medical information storage system of claim 12further comprising: an authorization module configured to detect whetherthe personal medical information storage device has been reported lostor stolen; the authorization module further configured to erase thecomputer readable storage medium if the personal medical informationstorage device has been reported lost or stolen.
 16. The medicalinformation storage system of claim 12 further comprising a forms moduleconfigured to store, receive, and transmit provider forms to or from thepersonal medical information storage device.
 17. The medical informationstorage system of claim 16 wherein the provider forms are pre-loaded onthe personal medical information storage device.
 18. The medicalinformation storage system of claim 12 further comprising a physiciannotes module configured to (a) store physician notes and files, (b)secure physician notes and files with a password, and (c) restrictaccess to physician notes and files to read-only access and delete-onlyaccess.
 19. The medical information storage system of claim 12 furthercomprising a sport module configured to store sports information to thepersonal medical information storage device, and where the sportsinformation comprises (a) exercise routine data, (b) performancehistories, (c) distance travelled, and (d) goals.
 20. A personal medicalinformation storage device comprising: a computer readable storagemedium configured to store both medical and non-medical information; anauthentication module stored on the computer readable storage medium,the authentication module configured to communicate with a remotemedical information storage device and verify that the personal medicalinformation storage device has not been reported (a) lost, or (b)stolen, and wherein the authentication module is configured to erase themedical and non-medical information of the computer readable storagemedium upon a determination that the medical information storage devicehas been lost or stolen; and a physician note module stored on thecomputer readable storage medium and comprising: an encrypted physiciannotes field; an encrypted physician files field for images and PDFs; asave functionality configured to restrict access to the encryptedphysician notes field and the encrypted physician files field toread-only access and delete-only access; and a form module configured tostore a plurality of doctor-specific forms for downloading on a generalpurpose computing device.